An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, We are seeking guidance regarding our Apple Developer Program account, which is currently under a Pending Termination Notice related to Section 3.2(f) of the Apple Developer Program License Agreement. The notice stated that our account had repeatedly submitted apps with unresolved guideline violations and that Apple believed these submissions were attempting to evade the review process. We want to make it clear that we never intended to mislead Apple or bypass the review process. We understand the seriousness of Apple's concerns and have taken the matter very seriously. Following the notice, we submitted an appeal to the App Review Board on June 4, 2026. In our appeal, we acknowledged the issues raised, explained the circumstances that led to the repeated submissions, and committed to implementing stronger internal review and compliance procedures. We also expressed our willingness to remove the app involved if necessary to ensure full compliance with Apple's policies. We have been members of the Apple Developer Program for several years and have always aimed to build products that comply with Apple's guidelines. We value the App Store ecosystem and would like the opportunity to address any concerns and continue serving our users responsibly. We want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team or the community on the best way to confirm our materials are under active review, and on any additional steps that would help. Thank you. Thank you for your time and any guidance you can provide.

Hello, My app submission has been waiting for review for 8 days, and there has been no status update or request for additional information. Submission ID: f9cc5319-693b-4809-8bcb-5eb0e8ad28bd I understand that review times can vary, but this is considerably longer than I have experienced before. Could an Apple representative please check whether the submission is progressing normally or if any action is required from my side? Thank you.

Hello, Our StoneEx iOS app (Apple ID 6782465590) was submitted for App Review on August 2, 2026 and has remained in “Waiting for Review” for almost two weeks without any change in status. We have contacted Apple Developer Support multiple times. Our existing support case is: Case ID: 20000133276837 So far, we have received only confirmations that our requests were received, but no substantive response or status update. We have also made repeated attempts to contact Developer Support by phone, including extended hold times, without reaching a specialist. There are no messages in Resolution Center, and we have not received any request for additional information or indication that something is missing from the submission. Could someone from Apple please check whether this submission or support case is stuck and, if appropriate, escalate Case ID 20000133276837 to the relevant App Review or Developer Support team? App: StoneEx Platform: iOS Apple ID: 6782465590 Submitted: August 2, 2026 Current status: Waiting for Review Support Case ID: 20000133276837 Thank you.

Hello, My app Jewel Coloring Go! (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on July 31, 2026. However, today is Auguse 9, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.

Hello, I have a single app record where the macOS platform completed review promptly and the iOS platform has been In Review for nine days. Both were submitted at the same time. App name: ProjectKiller Apple ID: 6796546956 Platforms: macOS and iOS, same app record Timeline: Aug 5, 12:22 AM — macOS 1.0 submitted (7 items). Review Completed. Aug 5, 12:22 AM — iOS 1.0 submitted (1 item). Status: In Review, unchanged since. Aug 14 — still In Review, 9 days. There is an earlier iOS submission from Aug 4 showing as Removed. I developer-rejected that one and resubmitted the following day. There are no messages in Resolution Center, no rejection, and no request for information. I have contacted Developer Support twice by phone, including case ID 20000134815022 on Aug 14, and have not had a substantive update. What I am trying to establish is whether anything is required from me, or whether this submission is simply sitting in the queue. The macOS approval on the same code base and the same metadata suggests the build itself is not the issue, but I would rather be told I have something to fix than keep waiting on a queue. I am not requesting expedited review. Any guidance appreciated. Thank you.

My app has been rejected about 3 times now with the reviewer only giving a generic message that a core function of the app is not working properly each time. No screenshots or mention of error messages ( which have been placed in the app purposely to tell users the reason for failure if it does happen). I have sent video clips of the function working normally on the same exact device and have many testers using the app daily with no issues. Two emails have gone out with no response this week and I have waited on hold with the support number for hours, eventually needing to hang up on my end. Needless to say, this is very frustrating as I cannot get my application out and have lost the confidence of users who were told the app is coming soon after testing. Any help here would be greatly appreciated

My first App Store submission has been in "Waiting for Review" since August 6, 2026 and has not yet moved to "In Review." App: Rotation Pool Scorer Apple ID: 6780028774 Bundle ID: com.michaelmanuele.arscorer Platform: iOS (initial release, not an update) Version / build: 1.0.0 (30) Submitted: August 6, 2026 at 11:04 AM EDT Submission ID: 56d82316-f8f5-4125-b025-5c8f0bef41b2 Items in submission: iOS App 1.0.0 (30) and one non-consumable in-app purchase, both showing "Waiting for Review" Support case: 20000135569120 (emailed August 12, 2026; no reply yet) I understand review times vary and that Apple's published figures are averages rather than commitments. I have confirmed the following on my end before posting: No messages in Resolution Center, and no email from App Review. Paid Applications and Free Applications agreements both Active, and both predate the submission date. Banking, tax (U.S. Form W-9) and Digital Services Act information all Active and complete. App Review Information is filled in, including notes covering the in-app purchase. The app requires no account or login, so no demo credentials apply. Nothing else from this account is submitted or blocking. I have not requested an expedited review, as I do not believe this situation meets the stated criteria, and I have not removed the submission from review. Is there anything further needed from me, or is this simply queue time? Any confirmation of the submission's status would be appreciated.

Hello Apple Developer Community, I’m looking for guidance regarding an unusually long App Review process for my first iOS app, Zivoo. The overall review and resubmission process has now been ongoing for more than a month. During the previous reviews, we received feedback from App Review. In response, the application was completely redesigned and the latest version contains a substantially revised core experience. The latest build is: App: Zivoo Platform: iOS Version: 2.1.4 (34) Submitted: August 10, 2026 Current status: Waiting for Review The App Store description, screenshots, metadata, and Review Notes have also been fully updated to reflect the redesigned application. Detailed testing instructions have been provided for App Review. After more than a month of working through the review process, responding to feedback, redesigning the application, and preparing a new submission, the latest build is still waiting for review without any visible progress. I have also contacted App Review Status support to confirm whether any additional action is required from our side. Could someone from Apple please check whether this submission is progressing normally or whether it may require additional attention? I would also appreciate hearing from other developers who have experienced a similar delay after substantially redesigning an application following App Review feedback. Thank you for any guidance or assistance.

I'm stuck on what looks like a backend / account-level TestFlight issue and want to ask if anyone has seen the same pattern. Symptoms (reproduced across three consecutive builds) App Store Connect ingests and processes each build successfully; it shows as "Testing" in TestFlight with no compliance warnings. Internal TestFlight install fails instantly on every tester device with: ▎ "The requested app is not available or does not exist." Device console (itunesstored) at install time: FAILED: TFBundleInstallation serverFailureReason="Error Downloading Install Data" userFailureReason="Requested app not available or does not exist" buildGroup=(null) phase=Failed previousPhaseDescription=ProcessingInstallInitiateResponse serverCode 200 Submitting the same build for external Beta App Review returns: 422 ENTITY_UNPROCESSABLE code: BETA_CONTRACT_MISSING buildGroup=(null) for builds that visibly show as "Testing", plus a persistent BETA_CONTRACT_MISSING, suggests the beta-contract / build-group record for the app is missing or corrupted on the backend. Already verified clean on the developer side Distribution certificate and provisioning profile valid; entitlements match the binary; codesign --verify --deep --strict passes. Free and Paid Apps Agreements both Active; no pending tasks (Banking, Tax complete). App Information, Pricing & Availability, Age Rating, Content Rights, Test Information all complete; build page shows no warnings. Reproduced with multiple testers on multiple iOS 17+ devices, in a fresh internal testing group, after device-side cleanup (sign-out / reinstall TestFlight). Re-uploading a fresh build does not clear it — so it is not bound to a specific binary. Questions Has anyone seen Error Downloading Install Data + buildGroup=(null) + BETA_CONTRACT_MISSING together on a single app? How did you resolve it? 2. Why does ProcessingInstallInitiateResponse return serverCode 200 while still failing with "app not available", for a build that shows as "Testing"? 3. Is there a documented path to request that engineering regenerate a corrupted beta-contract / build-group record, beyond a standard support case? Any pointers appreciated — happy to share device logs / sysdiagnose if useful.

Hello Apple Developer Community, I submitted my first iOS app for App Review, but it has been stuck in “Waiting for Review” for 5 days, and the review has not started yet. I also contacted Apple Developer Support and opened a support ticket because I wanted to understand if there was an issue with my submission, but I have not received a response yet. I would like to ask other developers if anyone is currently experiencing the same issue. App Information App Name: AksiyonSoft Tools -Calculator Bundle ID: com.aksiyonsoft.calculator Platform: iOS Status: Waiting for Review Submitted: August 9, 2026 Waiting time: 5 days This is our first iOS app submission, so I would especially appreciate hearing from developers who have recently experienced a similar situation. Is there currently a delay in the App Review queue, or could there be an issue with my submission that is preventing the review from starting? Has anyone else been waiting for 5 days or longer for their app to enter review recently? Any information or recent experience would be greatly appreciated. Thank you.

Hello everyone, I submitted my app to App Review five days ago, and its status is still showing “Waiting for Review.” There have been no messages in the Resolution Center and no requests for additional information. The same app was approved on the Google Play Store and has already been live there for a week. I understand that Apple’s review process is different and that review times can vary, but five days without entering the review stage seems longer than usual. Is anyone else currently experiencing similar delays? Should I simply continue waiting, or would you recommend contacting Apple Developer Support at this point? Thank you for any advice or feedback.

I recently submitted a new app for App Review, and it has been in “Waiting for Review” for longer than expected. I understand that review times can vary depending on Apple’s current workload, but I wanted to ask if other developers are currently experiencing similar delays. The submission is still showing “Waiting for Review”, and there are no messages or issues shown in App Store Connect. Is there currently a longer-than-usual App Review wait time? And is there anything I should do while waiting, or is it best to simply wait for the review to begin? Would appreciate any insight from developers who have recently gone through the same situation. Thank you!

I understand that they/you are probably being flooded by a lot of AI slop apps or other excuses, but submitting an app 3 weeks ago and it being stuck in Waiting for Review (not first app live on app store either) is beyond a joke. Lodge a support request (not expedited review request) and to get back a generic you will be notified when it changes to In review is not the sort of support help you would expect either. This sort of delay impacts businesses (time and money) and needs to be fixed by either putting more reviewers on - OR better still move more towards the Automated review process Google uses. meantime it still sits there in waiting for review.

Hi, my app has been "waiting for review" for eight days, far past the general 24-to-48-hour period. For note, I had cancelled a previous request and resubmitted with an updated build and have been further updating the build from TestFlight feedback. I would appreciate prompt response and review, as the wait for the review and subsequent steps that have not taken place carry business implications for the app. Thanks in advance!

Hello, I’m looking for guidance regarding an unusually long App Review process for my app, Auto Deal. The app was originally submitted on July 2, 2026. It eventually entered “In Review,” but remained there for an unusually long period without any update or decision. After waiting for a long time with no progress, I deleted the submission and uploaded it again. On the second submission, we again experienced a long delay. The app was eventually reviewed and rejected because of an issue that occurred when tapping the “Confirm” button inside the app. I immediately fixed the exact issue identified by App Review and submitted the corrected build. The corrected submission then entered “In Review,” but once again remained there for a long period without any further feedback or decision. After waiting again with no progress, I deleted the submission and uploaded a new build. When the same prolonged delay continued, I deleted that submission and submitted another fresh build. I understand that deleting and resubmitting can restart the review process. However, I only took these steps after repeatedly experiencing unusually long periods in review without any decision or explanation. Throughout this entire process, I have contacted Apple Developer Support multiple times and submitted three expedited review requests, but the issue remains unresolved. The app is complete and already available on Google Play. We have customers waiting for the iOS version, and this prolonged review process has significantly delayed our business launch. I am not requesting another expedited review through this post. I am trying to understand why this keeps happening and whether there is an issue with the app submission, my developer account, or the review process that requires action from my side. If an Apple engineer or App Review representative can look into this situation or advise me on the appropriate next step, I would greatly appreciate it. Thank you.

I submitted first version of my app on Aug-4 and since then status is stuck in "Waiting for Review". I tried calling support but the phone call keeps me on hold for hours and no response to emails.

Version 1.1.0 of our app was rejected last week for an incentivized review feature. We fully removed it and resubmitted as 1.1.1 on Aug 8, but it's now been 6+ days with no status change. We've submitted an expedite request and contacted Developer Support by phone without resolution. Could someone advise on next steps? Thank you! App ID: 6753783729 Submission ID: be06df46-14a1-4f9e-84e1-ff5b016aadbf

Hello, Our app FlowCast (Apple ID: 6790962652, iOS, version 1.0) was submitted on July 17, 2026 and has remained in "Waiting for Review" for ten days. It has never moved to "In Review". There are no messages in the Resolution Center and no requests for additional information. This is the first App Store submission for this app. All required metadata, assets, permissions and compliance information were provided at submission. On July 24, 2026 we completed an outstanding DSA trader status declaration on the account, in case that was blocking the submission; there has been no change since. An expedited review request was submitted on July 26, 2026. Could you please confirm whether the submission is progressing normally, or whether there is an issue on our side that we need to resolve? Thank you.

Hi my app is still "Waiting for Review" since almost a week now. Is it normal? Thank you!

Player Bash iOS 1.2.0 stuck in “Waiting for Review” for 10 days Hi Apple Developer Community, Our app, Player Bash, iOS version 1.2.0, was submitted for App Review on August 3, 2026 at 6:33 PM and has remained in “Waiting for Review” since then. Submission Details App: Player Bash Platform: iOS Version: 1.2.0 Submission ID: 19334d6c-3717-4d80-aebb-f6bce43bd68f Submitted: August 3, 2026 at 6:33 PM Current Status: Waiting for Review Support Case ID: 20000132723383 The submission has not moved to “In Review”, and there are no messages or requests for additional information in App Store Connect or the Resolution Center. We have already contacted Apple Developer Support regarding the delayed review and are still waiting for a response. We have also checked App Store Connect, and there do not appear to be any outstanding issues or actions required from our side. Could someone from Apple please confirm whether there is currently an App Review backlog or whether there is anything we should do from our side to help move this submission forward? We would really appreciate any guidance or assistance. Thank you.